Agricultural Yield Prediction¶

The purpose of this analysis is the creation and comparison of several machine learning regression models to see how good they are at predicting agricultural yield based on multiple factors.

1. Data Collection¶

The analysis will be based on the 'Synthetic Agricultural Yield Prediction Dataset' available on kaggle.com. The dataset is released under MIT Licence:

Copyright (c) 2013 Mark Otto. Copyright (c) 2017 Andrew Fong.

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

This dataset is synthetic and generated for the purpose of machine learning practice. It is not based on real-world data, hence no acknowledgments to external sources are necessary. SOFTWARE.

This dataset consists of 16,000 records containing information on agricultural yield, such as soil quality, fertilizers, seed variety, irrigation, and weather conditions. Detailed information on each feature can be found below. All these factors may contribute to the yield. Based on these features, we'll create several machine learning models and compare their ability to correctly predict the yield on test data.

Let's start by installing the libraries we're going to need:

Train and test data is contained in separate CSV files. Let's download the data and store it in two DataFrames: df_train and df_test, and then, let's have a glance at the initial records:

Data Description¶

Looks like both datasets contain just numerical data. Let's have a look at some basic information about the two DataFrames:

The first DataFrame, df_train, consists of 16,000 rows, each of which represents a single yield sample, and 7 columns, each of which represents a single feature. The second DataFrame, df_test, consists of 4,000 rows and 7 columns.

The data is complete, there are no missing values. Two of the columns, Seed_Variety and Irrigation_Schedule, are of the integer type (int). The remaining five columns are of the floating-point type (float).

Let's have a closer look at the particular columns. Here's how they're described in the dataset:

• Soil_Quality: Soil quality index, ranging from 50 to 100
• Seed_Variety: Binary indicator of seed variety, where 1 represents a high-yield variety
• Fertilizer_Amount_kg_per_hectare: The amount of fertilizer used in kilograms per hectare
• Sunny_Days: The number of sunny days during the growing season
• Rainfall_mm: Total rainfall received during the growing season in millimeters
• Irrigation_Schedule: The number of irrigations during the growing season
• Yield_kg_per_hectare: The agricultural yield in kilograms per hectare

The last column, Yield_kg_per_hectare, serves as the target variable for prediction.

2. Exploratory Data Analysis (EDA) and Feature Engineering¶

Data Preprocessing and Cleaning¶

Before we start the data analysis, the data should be cleaned and preprocessed if necessary. This process includes:

• removing redundant rows and columns
• handling missing data
• handling duplicates
• data transformations

At this stage, we'll start analyzing the data only in a very general manner. Next, we'll visualize the data and examine it more closely. If necessary, we'll go through some of the steps described above again, like removing redundant rows and columns or data transformations.

Removing Redundant Rows and Columns¶

To start with, let's check whether our DataFrame contains columns or rows that can be removed.

As far as columns are concerned, we usually remove columns with unique values that identify the particular records, like ID or Name. There are no such columns in our DataFrame, though.

Missing Data¶

As shown before, there is no missing data in our DataFrame, so there's nothing to do as far as this is concerned. If there were missing data, we could handle it in one of a couple possible ways. For example, we could fill in the missing values with mean, median, or interpolated values, or values calculated in a different way. We could also completely remove the rows or columns containing missing data.

Duplicates¶

The next thing to take care of is duplicates. Duplicates are repeated rows. Let's check if there are any duplicates at all in our DataFrame:

As we can see, there are no duplicates in our DataFrame.

Data Transformations¶

We don't actually need to perform any data transformations at this point. All data in our DataFrame is numerical. All numerical data will be scaled to align with the normal distribution (mean equal to 0, standard deviation equal to 1), but not until we're done with data visualizations because it would be unintuitive to use such data there.

Although this is not necessary, but just for demonstrational purposes let's change the column headers to be written as separate words instead of being joined by underscores and all lowercase:

Our data has been preprocessed and cleaned. In the next step, we'll visualize the data.

Data Visualization¶

We visualize data to graphically represent the relationships between features and the quantitative characteristics of the particular features. This way we can understand our data way better.

We're particularly interested in the relationships between the target feature, so the one our models will try to predict, and the other features. The target feature is yield kg per hectare.

The data visualization process will include the following:

• a statistical summary of the numeric features for the entire dataset
• handling outliers, so leaving, replacing, or removing them
• examination of correlations between features and, if necessary, removing features that are very weakly correlated with the target feature

A Statistical Summary of the Numeric Features¶

Let's start with a statistical summary of the numeric features for the entire dataset:

Here we can see the statistics for all the columns. These include:

• count - the number of records for which there is a value
• mean - the arithmetic mean
• std - the standard deviation
• min - the minimum value
• 25% - the first quartile, dividing the dataset into 2 parts, where the first part contains 25% of the records with values less than or equal to the value for this quartile, and the other part contains 75% of the records with values greater than or equal to the value for this quartile
• 50% - the median, or the second quartile, dividing the dataset into 2 parts in such a way that 50% of the records have values less than or equal to the median, and the remaining 50% of the records have values greater than or equal to the median
• 75% - the third quartile, dividing the dataset into 2 parts, where the first part contains 75% of the records with values less than or equal to the value for this quartile, and the other part contains 25% of the records with values greater than or equal to the value for this quartile
• max - the maximum value

To better understand the above statistics, let's have a look at the first column as an example:

Here's what we can conclude from the statistics:

• all 16,000 records have a value in this column
• the mean of soil quality is about 74.76
• the standard deviation is about 14.53
• the minimum value for this feature is about 50.01
• 25% of the samples have a soil quality of about 62.17 or less, and the remaining 75% have a soil quality of about 62.17 or more
• half the samples have a soil quality of about 74.68 or less, and the other half - about 74.68 or more
• 75% of the samples have a soil quality of about 87.38 or less, and the remaining 25% have a soil quality of about 87.38 or more
• the maximum soil quality for a sample is 99.998101

In a similar way we interpret the statistics for the other features.

Outliers¶

Outliers are values that significantly differ from the other values typical of a feature. There are multiple ways to determine which values should be considered outliers. In pandas, the method of interquartile range (IQR) is used.

In our analysis, we'll be using boxplots to graph the distribution of values for each feature. Let's have a look at an example. Here's the boxplot for the feature rainfall mm:

The left and right sides of the box correspond to the first (25%) and third (75%) quartile respectively, and the vertical line inside the box represents the median. To either side of the box, there are whiskers that reach up to the minimum value on the left and the maximum value on the right, excluding the outliers. The outliers are represented as small circles on both sides.

As stated above, the outliers visible in the plot were determined using the method of interquartile range (IQR). The range of the whiskers was calculated using the following formula:

• lower bound = Q1 - 1,5 x IQR
• upper bound = Q3 + 1,5 x IQR

where:

• Q1 - first quartile (25%)
• Q3 - third quartile (75%)
• IQR = Q3 - Q1

The values beyond these bounds are outliers.

There are three approaches to handling outliers:

• we can just leave them as is
• we can replace them with other values (e.g. the mean, the median, the lower and upper bounds calculated above, and so on)
• we can remove the rows that contain the outliers

Before we start analyzing the outliers for the particular features, let's create two functions that will make this task easier:

• The first function will display some basic information about the outliers, like the first and third quartile, the interquartile range, the lower and upper bounds defining the outliers, the number of outliers below the minimum value, above the maximum value, and altogether. The function will also enable us to optionally display the sorted records the outliers are contained in.
• The other function will remove rows with values beyond a given range. This may be the range containing the outliers, but it can also be any other range because sometimes we'll only want to remove some rows with outliers. Additionally, this function will display information about the size of the dataset before the rows are removed, the number of rows removed, and the size of the dataset after removing the rows.

The first function is defined like so:

And here's the definition of the other function:

Now we can start analyzing the outliers for the particular features.

soil quality¶

Here's the boxplot for the feature soil quality:

As we can see, there are no outliers for this feature.

seed variety¶

Here's the boxplot for the feature seed variety:

There are no outliers for this feature either.

fertilizer amount kg per hectare¶

Here's the boxplot for the feature fertilizer amount kg per hectare:

As we can see, there are no outliers for this feature either.

sunny days¶

Here's the boxplot for the feature sunny days:

As we can see, there are quite a few outliers below the minimum value and above the maximum value. We have to decide how to handle them. Let's use our function to analyze the outliers quantitatively:

Most of the outliers lie relatively close to the lower and upper bounds, so we can keep them. Removing all rows with outliers could deprive us of a fair amount of useful information about the data contained in the other columns of those rows. But some outliers are pretty distant from the bounds, in particular, those with values below 60 and above 140. Let's count them:

There are just two rows with such outliers, so let's use our function to remove them:

rainfall mm¶

Here's the boxplot for the feature rainfall mm:

As we can see, there are some outliers below the minimum value and some above the maximum value. We have to decide how to handle them. Let's use our function to analyze the outliers quantitatively:

In this case, the outliers lie relatively close to the lower and upper bounds, so let's just keep them.

irrigation schedule¶

Here's the boxplot for the feature irrigation schedule:

As we can see, there are no outliers below the minimum value, but there are some at specific intervals above the maximum value. We have to decide how to handle them. Let's use our function to analyze the outliers quantitatively:

There are 214 outliers altogether. We could remove them, but as they are not very distant from the upper bound, let's leave them as is.

Let's have a look at the statistics again after removing some of the rows:

There is only a slight difference because only a few rows were removed.

Correlations Between Features¶

Before we start analyzing the particular features one by one, let's have a closer look at the relationships between them. In particular, we're interested in how the features correlate with the target feature, which is yield kg per hectare.

Let's plot the pairwise relationships between the features first:

Here we can see some linear relationships, like for example between irrigation schedule and yield kg per hectare, as well as some nonlinear relationships, like for example between sunny days and yield kg per hectare. Sometimes there are no visible relationships, like for example between fertilizer amount kg per hectare and sunny days.

Let's try to express the correlations between features numerically:

The values that we can see here are all between -1 and 1. Here's an explanation:

• the value 1 - full positive correlation (as the value of one feature increases, the value of the other feature increases the same way)
• the closer the value is to 1 the stronger the positive correlation between the features (as the value of one feature increases, the value of the other feature increases too)
• the closer the value is to -1 the stronger the negative correlation between the features (as the value of one feature increases, the value of the other feature decreases)
• the closer the value is to 0 the weaker the correlation between the features - it may be slightly positive or negative
• the value -1 - full negative correlation (as the value of one feature increases, the value of the other feature increases the same way but in the opposite direction)

The correlations between any two features can be found at their intersection. At the intersection of the same feature (e.g. the row sunny days and the column sunny days), the correlation is always 1.

For example, let's have a look at the correlation between fertilizer amount kg per hectare and yield kg per hectare. The value at the intersection of the two features is 0.284794, which is a moderate positive correlation. As the fertilizer amount kg per hectare increases, so does the yield kg per hectare. In this case, it's pretty intuitive: we use fertilizers to get more crops after all.

The way we present the correlations above may be slightly unreadable if there are more features. A more readable way of presenting the correlations is by means of a heatmap, where the particular values are assigned colors. Let's use the seaborn library to create a heatmap for our data:

We used a mask to hide the top half of the matrix, where the values are repeated. On the right, we can see the color map used in the heatmap. The values are displayed with a precision of 3 decimal places.

By using the colors, we can immediately see which features are correlated with which other features and to what degree. For most of the pairs, there's very weak positive or negative correlation. The pairs with the strongest positive correlation are:

• yield kg per hectare and seed variety (0.680)
• yield kg per hectare and irrigation schedule (0.561)
• yield kg per hectare and fertilizer amount kg per hectare (0.285)
• yield kg per hectare and soil quality (0.109)
• yield kg per hectare and sunny days (0.099)

The pair with the strongest negative correlation is:

• yield kg per hectare and rainfall mm (-0.252)

For the other pairs, the absolute values of the correlations are less than 0.02, which are very weak correlations.

In case of very strongly correlated features, we face the problem of feature colinearity, which may have a negative impact on machine learning models, so it's recommended to remove one of the features in each of such pairs. Strongly correlated features convey the same information, so there's no need for this kind of redundancy. We can remove either feature in each pair, but we usually keep the one that is easier to interpret or just seems more important. If none of the features seems more important than the other, we just arbitrarily remove one of them.

By strongly correlated features we mean pairs with correlations close to 1 or -1.

In our dataset, we don't have any colinear features, though, so we're not going to remove any of them.

The most important correlations for us are the ones between the target feature, yield kg per hectare, and the other features. Let's have a look at these values, as well as the absolute values of the correlations. Let's label the type of each correlation and determine its strength. We'll consider a correlation to be very weak if its absolute value is below 0.1:

As we can see, there is one very weak correlation, between yield kg per hectare and sunny days. We could remove the feature sunny days, but, as it's so close to the lower bound of 0.1, we can also keep it, which is what we are going to do.

Quantitative Analysis of the Features¶

Now we can start the analysis of the features. Let's create a set of histograms for all numeric features first:

Let's now examine all the features one by one.

soil quality¶

Here's the distribution of this feature:

As we can see, the number of samples is distributed rather evenly. There are slightly more samples with worse soil quality, but the difference isn't significant. Let's now examine the relationship between the feature soil quality and the target feature, yield kg per hectare:

The value of the correlation between soil quality and yield kg per hectare is 0.109 and this is a weak positive correlation. As soil quality increases, so does yield kg per hectare.

seed variety¶

Here's the distribution of this feature:

As we can see, there are twice as many samples with a high value of seed variety than with a low one. Let's now examine the relationship between the feature seed variety and the target feature, yield kg per hectare:

The value of the correlation between seed variety and yield kg per hectare is 0.680 and this is a strong positive correlation, so higher yield kg per hectare matches higher seed variety.

fertilizer amount kg per hectare¶

Here's the distribution of this feature:

As we can see, the samples are distributed pretty evenly, with slightly more samples in the higher range. Let's now examine the relationship between the feature fertilizer amount kg per hectare and the target feature, yield kg per hectare:

The value of the correlation between fertilizer amount kg per hectare and yield kg per hectare is 0.285 and this is a moderate positive correlation. As fertilizer amount kg per hectare increases, so does yield kg per hectare.

sunny days¶

Here's the distribution of this feature:

As we can see, the number of samples with a medium value of sunny days is the greatest. Let's now examine the relationship between the feature sunny days and the target feature, yield kg per hectare:

The value of the correlation between sunny days and yield kg per hectare is 0.099 and this is a weak positive correlation. As sunny days increases, yield kg per hectare increases too.

rainfall mm¶

Here's the distribution of this feature:

As we can see, the number of samples with a medium value of rainfall mm is the greatest. Let's now examine the relationship between the feature rainfall mm and the target feature, yield kg per hectare:

The value of the correlation between rainfall mm and yield kg per hectare is -0.252 and this is a moderate negative correlation. As rainfall mm increases, yield kg per hectare decreases.

irrigation schedule¶

Here's the distribution of this feature:

As we can see, the number of samples with a lower value of irrigation schedule is the greatest. Let's now examine the relationship between the feature irrigation schedule and the target feature, yield kg per hectare:

The value of the correlation between irrigation schedule and yield kg per hectare is 0.561 and this is a rather strong positive correlation. As irrigation schedule increases, so does yield kg per hectare.

Getting the Data Ready for Model Training¶

The following steps deal with feature engineering and preparing the data for model training. It's crucial to perform these operations in due order, so as to avoid data leakage and maintain test data integrity, which is especially important in the context of model evaluation that comes afterward.

In particular, here's the order we should stick to:

1. Splitting the data into a training set and a test set
2. Feature Engineering (e.g. encoding categorical data, scaling numerical data)

As far as feature engineering is concerned, we first encode categorical data into numerical data and only then do we scale it. As our dataset doesn't contain any categorical data, there's no encoding to perform.

Splitting the Data into a Training Set and a Test Set¶

Before we apply the operations related to feature engineering, we should split our data into two separate sets, a training set and a test set. We use the train_test_split method from the sklearn library to do that.

However, our data is already contained in two separate sets, so we don't have to split it. We already have the training set (df_train) and the test set (df_test).

What we have to do, though, is separate the target column from the rest:

X_train and X_test are input data, so all the features except the one we want to predict.
y_train and Y_test are the target feature, which we want to predict.

When we use the train_test_split method, we usually set the test_size parameter to a value that represents the split proportions. For example, if we set test_size = 0.2, 20% of the data is allocated to the test set and the remaining 80% of the data is allocated to the training set. As our data was originally split into the two sets, let's find out which split proportion was used:

As we can see, here's the proportion is also 20:80.

To sum up, we now have the following:

• X_train - the feature training set, used to train the models
• X_test - the feature test set, used to evaluate the models
• y_train - the target training set
• y_test - the target test set

Feature Engineering¶

Feature engineering is a broad topic, that, in particular, includes:

• feature creation:
  • domain-specific (based on domain knowledge)
  • data-driven (based on patterns observed in the data)
  • synthetic (by combining existing features)
• feature transformation:
  • normalization (rescaling the features to a similar range, eg. between 0 and 1, to prevent any feature from dominating other features)
  • scaling (rescaling the features to a similar scale, eg. a standard deviation of 1, to ensure all features are considered equally)
    • min-max scaling (rescaling the features to a specific range, eg. between 0 and 1, by substracting the minimum value and dividing by the range)
    • standard scaling (rescaling the features to have a mean of 0 and a standard deviation of 1 by subtracting the mean and dividing by the standard deviation)
    • robust scaling (rescaling the features to be robust to outliers by dividing them by the interquartile range)
  • encoding (transforming categorical data to numerical data, eg. one-hot encoding and label encoding)
  • mathematical transformations (to change the distribution or scale of the features, eg. logarithmic, square root, or reciprocal transformation)
• feature extraction
  • dimensionality reduction (reducing the number of features while retaining important information, eg. PCA, t-SNE)
  • feature combination (combining multiple features to create a new one)
  • feature aggregation (creating new features by aggregating existing ones, eg. a feature being the sum or mean of other features)
  • representation transformation (new representation of a feature or its part)

Naturally, it doesn't mean we have to perform all these operations on our data. It all depends on what type of data we're dealing with and what we want to achieve.

Our dataset contains only numerical data. As far as feature engineering is concerned, we're going to perform just one operation, standard scaling. There's a ready-to-use library to take care of that:

It's important to initially perform the scaling only on the training set, so that the data from the test set doesn't influence the scaling process. This will prevent data leakage. Next, we'll apply the parameters calculated this way, mean and standard deviation, to the test set.

Let's have a look at the data in the training set before scaling:

Let's scale the data:

Let's now have a look at the data after scaling:

The data was scaled in such a way that the mean is 0 and the standard deviation is 1. Now we can move on to model training.

3. Training the Models¶

We're going to train several traditional ML models and compare the results using some easy-to-understand metrics.

We'll start with the traditional machine learning models and then we'll move on to the MLP.

Traditional Machine Learning Models¶

Let's start by importing the traditional machine learning models and metrics:

The process of training and evaluating the models is repetitive and consists of the following steps for each model:

1. creating the model with a set of hyperparameters (we'll start with just the default values of the hyperparameters)
2. training the model
3. using the model to predict the target feature in the test set
4. evaluating the model

For ease of use, we'll put all the models in a dictionary. We'll create them with just the default values of the hyperparameters for now. An exception to this rule will be the random_state hyperparameter where applicable, used to ensure reproducibility of the results.

Some hyperparameters may require finetuning later on, but we won't know that before training the models. Each model has lots of hyperparameters, some of which can be set to a whole range of different values, but let's not be bothered by that right now.

So, here are the models:

To make the task easier, let's define some functions. Let's start by defining a function that will evaluate a model:

In order to understand what the function does, we might need a quick refresher on all the metrics it uses:

Mean Squared Error (MSE) - it calculates the average squared difference between predicted and actual values

$ \text{MSE} = \frac{1}{n} \sum_{i=1}^{n} (y_i - \hat{y}_i)^2 $

where:
$ y_i $ - actual value
$ \hat{y}_i $ - predicted value
$ n $ - number of samples

It heavily penalizes large errors because they are squared, which makes it sensitive to outliers.
The Mean Squared Error (MSE) is easier to interpret if we take a square root of it, which gives us the Root Mean Squared Error (RMSE). The result tells us by how much the predictions deviate.

Mean Absolute Error (MAE) - it calculates the average absolute difference between predicted and actual values

$ \text{MAE} = \frac{1}{n} \sum_{i=1}^{n} |y_i - \hat{y}_i| $

It penalizes all errors equally, which makes it less sensitive to outliers in comparison with MSE.

Mean Absolute Percentage Error (MAPE) - it calculates the average percentage difference between predicted and actual values, relative to the actual values

$ \text{MAPE} = \frac{100}{n} \sum_{i=1}^{n} \left| \frac{y_i - \hat{y}_i}{y_i} \right| $

It represents errors as a percentage, which makes it easier to understand.

R² Score (Coefficient of Determination) - it measures how well the model explains the variance in the actual target values

$ R^2 = 1 - \frac{\text{SS}_{\text{res}}}{\text{SS}_{\text{tot}}} $

where:
$ \text{SS}_{\text{res}} = \sum_{i=1}^{n} (y_i - \hat{y}_i)^2 $ (Residual Sum of Squares)
$ \text{SS}_{\text{tot}} = \sum_{i=1}^{n} (y_i - \bar{y})^2 $ (Total Sum of Squares)
$ \bar{y} $ - mean of the actual values

It's a relative measure that compares the model’s performance to the mean of the actual values.

Residuals Plot - it measures the model's performance

The residuals plot of a model has some characteristics that we should examine to evaluate the model's performance. In particular:

• the residuals should be randomly scattered around the horizontal line at y = 0 - it means the model captures the structure of the data correctly,
• there should be no clear patterns in the scatter plot, like a wave or parabola - if there are, it means the model doesn't capture some systematic behavior in the data,
• the spread of the residuals shouldn't increase or decrease as predictions grow - this would indicate non-constant behavior,
• there shouldn't be many outliers (points far away from the horizontal line at y = 0) - if there are, they indicate poorly predicted samples.

And here's a function to train and evaluate a model:

Let's now train and evaluate all the models one by one:

Linear Regression¶

Linear Regression is a model that estimates the linear relationship between a scalar response (dependent variable) and one or more explanatory variables (independent variable).

Interpretation:

The root of the Mean Squared Error (MSE) is about 50, which is about 4% of the target range (which is about 1300). This result is pretty good.

The Mean Absolute Error (MAE) is about 40, which is about 3.2% of the target range. This result is acceptable.

The Mean Absolute Percentage Error (MAPE) is 0.0643, which means the predictions are on average 6.43% off the true values. This result is very good.

The R-Squared Score is about 0.94, which means the model explains about 94% of the variance in the target variable. This result is very good.

The residuals are randomly scattered around the horizontal line at y = 0, therearee no clear patterns in the scatter plot, the spread of the residualdoesn't't increase or decrease as predictions gr, and , thearen't be many outli, so the model seems to be performing pretty well.es.

K-Nearest Neighbors (KNN)¶

K-Nearest Neighbors (KNN) is a model that classifies data points based on the majority class of their nearest neighbors in the feature space.

Interpretation:

The root of the Mean Squared Error (MSE) is about 59, which is about 4.5% of the target range (which is about 1300). This result is pretty good.

The Mean Absolute Error (MAE) is about 47, which is about 3.6% of the target range. This result is acceptable.

The Mean Absolute Percentage Error (MAPE) is 0.0759, which means the predictions are on average 7.59% off the true values. This result is very good.

The R-Squared Score is about 0.91, which means the model explains about 91% of the variance in the target variable. This result is very good.

The residuals are randomly scattered around the horizontal line at y = 0, there are no clear patterns in the scatter plot, the spread of the residuals doesn't increase or decrease as predictions grow, and there aren't many outliers, so the model seems to be performing pretty well.

Decision Tree¶

A Decision Tree is a tree-structured model that splits the data based on specific feature thresholds to create decision rules. If not pruned, may easily overfit.

Interpretation:

The root of the Mean Squared Error (MSE) is about 77, which is about 6% of the target range (which is about 1300). This result is just fine.

The Mean Absolute Error (MAE) is about 61, which is about 4.7% of the target range. This result is acceptable.

The Mean Absolute Percentage Error (MAPE) is 0.0970, which means the predictions are on average 9.70% off the true values. This result is good.

The R-Squared Score is about 0.85, which means the model explains about 85% of the variance in the target variable. This result is good.

The residuals are randomly scattered around the horizontal line at y = 0, there are no clear patterns in the scatter plot, the spread of the residuals doesn't increase or decrease as predictions grow, and there aren't many outliers, so the model seems to be performing pretty well.

Random Forest¶

A Random Forest is a set of decision trees where the predictions are averaged, which reduces overfitting.

Interpretation:

The root of the Mean Squared Error (MSE) is about 55, which is about 4% of the target range (which is about 1300). This result is pretty good.

The Mean Absolute Error (MAE) is about 44, which is about 3.4% of the target range. This result is acceptable.

The Mean Absolute Percentage Error (MAPE) is 0.07, which means the predictions are on average 7% off the true values. This result is very good.

The R-Squared Score is about 0.92, which means the model explains about 92% of the variance in the target variable. This result is very good.

The residuals are randomly scattered around the horizontal line at y = 0, there are no clear patterns in the scatter plot, the spread of the residuals doesn't increase or decrease as predictions grow, and there aren't many outliers, so the model seems to be performing pretty well.

Gradient Boosting¶

Gradient Boosting is a model that builds decision trees sequentially, each time correcting the errors of the previous trees.

Interpretation:

The root of the Mean Squared Error (MSE) is about 52, which is about 4% of the target range (which is about 1300). This result is pretty good.

The Mean Absolute Error (MAE) is about 42, which is about 3.2% of the target range. This result is acceptable.

The Mean Absolute Percentage Error (MAPE) is 0.0669, which means the predictions are on average 6.69% off the true values. This result is very good.

The R-Squared Score is about 0.93, which means the model explains about 94% of the variance in the target variable. This result is very good.

The residuals are randomly scattered around the horizontal line at y = 0, there are no clear patterns in the scatter plot, the spread of the residuals doesn't increase or decrease as predictions grow, and there aren't many outliers, so the model seems to be performing pretty well.

Extra Trees¶

Extra Trees is a set of decision trees, just like Random Forest, but the splits in the trees are random, which makes the training faster and reduces variance.

Interpretation:

The root of the Mean Squared Error (MSE) is about 56, which is about 4.3% of the target range (which is about 1300). This result is pretty good.

The Mean Absolute Error (MAE) is about 45, which is about 3.5% of the target range. This result is acceptable.

The Mean Absolute Percentage Error (MAPE) is 0.0708, which means the predictions are on average 7.08% off the true values. This result is very good.

The R-Squared Score is about 0.92, which means the model explains about 94% of the variance in the target variable. This result is very good.

The residuals are randomly scattered around the horizontal line at y = 0, there are no clear patterns in the scatter plot, the spread of the residuals doesn't increase or decrease as predictions grow, and there aren't many outliers, so the model seems to be performing pretty well.

XGBoost¶

XGBoost is an efficient and scalable implementation of gradient boosting, including features like regularization and early stopping.

Interpretation:

The root of the Mean Squared Error (MSE) is about 55, which is about 4% of the target range (which is about 1300). This result is pretty good.

The Mean Absolute Error (MAE) is about 44, which is about 3.4% of the target range. This result is acceptable.

The Mean Absolute Percentage Error (MAPE) is 0.0698, which means the predictions are on average 6.98% off the true values. This result is very good.

The R-Squared Score is about 0.92, which means the model explains about 94% of the variance in the target variable. This result is very good.

The residuals are randomly scattered around the horizontal line at y = 0, there are no clear patterns in the scatter plot, the spread of the residuals doesn't increase or decrease as predictions grow, and there aren't many outliers, so the model seems to be performing pretty well.

Model Comparison¶

We now have the metrics of all the models. The question is, how do they compare? As we trained the models, we stored all the metrics. Let's put them in a list:

Now, let's create a DataFrame with all the metrics for each model:

Next, let's visualize the metrics by creating a bar plot for each of them. This way, we'll be able to compare all the metrics for all the models. Let's wrap the code in a function:

Let's call the function with our df_metrics DataFrame:

Almost all of the metrics are best (lowest) for the Linear Regression model, so let's try to make it even better by tuning its hyperparameters.

Hyperparameter Tuning¶

Now that we have selected one particular model, we can fine-tune it by testing different values of hyperparameters. We could do it by hand, but this would be tedious and time-consuming. There's a solution we can use, GridSearchCV.

The name GridSearch consists of two parts:

• 'GridSearch' - because there's a grid with different values of hyperparameters and every combination of them is tested,
• 'CV' (which stands for Cross Validation) - because the dataset is split into multiple folds and different train-test combinations are evaluated.

GridSearchCV tests all the combinations of hyperparameters and finds the best one.

In order to use GridSearchCD, we have to import it from scikit-learn:

Let's create the grid of hyperparameters for the selected model:

Now, let's fit the GridSearchCV:

Now that we know which hyperparameters are the best, let's use them to train our model:

Now we can train and evaluate the model:

Interpretation:

Mean Squared Error (MSE) is now the same as before (2563.06).
Mean Absolute Error (MAE) is now the same as before (40.58).
Mean Absolute Percentage Error (MAPE) is now the same as before (0.064).
R-Squared Score is now the same as before (0.9356).

The metrics haven't improved through hyperparameter tuning. But our model performs really well anyway.

Conclusion¶

Depending on the characteristics of our dataset, we can take a different approach to the machine learning process. We can choose one of the traditional machine learning models or a deep learning model. Here we trained just the former.

Before we train at least a couple models, it's really hard to say which model is optimal. Sometimes the traditional models perform better, sometimes the deep learning models are optimal.

Training multiple models allows us to compare the metrics and then fine-tune the model where they are the best, for example by tuning the hyperparameters. This process may improve the model's performance, but it isn't always the case.

To sum up, there is no one and only correct approach or model. We should always try out at least a few and compare the results. Ultimately, we should pick the model that performs best and use it to work on data of the same kind. We must remember, though, that it doesn't have to be the optimal model for other types of data.